Caching core JavaScript bundles

ABSTRACT

A method including retrieving application code of a webpage comprising a core code JavaScript bundle and a dynamic JavaScript bundle. The method transmitting to a user device of a user a service worker and the core code JavaScript bundle, wherein the core code JavaScript bundle is transmitted from the cache of the content delivery computer and is stored in a long-term cache memory of the user device. Facilitating a display of the webpage in a browser of the user device using the custom application code JavaScript bundle, and the core code JavaScript bundle. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation-in-Part and claims the benefit ofU.S. Non-Provisional application Ser. No. 16/264,509, filed Jan. 31,2019. U.S. Non-Provisional application Ser. No. 16/264,509 isincorporated herein by reference in its entirety.

TECHNICAL FIELD

This disclosure relates generally to using a service worker to cacheJavaScript application code in a content delivery server.

BACKGROUND

Conventional approaches for downloading a webpage for display on acomputing device can take too long to complete due to the complexity ofcomputer-run processes run for each webpage, such as a client-sideprocess, which causes a viewer of the webpage to have to wait for thewebpage to download and display. Moreover, each time another webpage isrequested, a web server initiates the same computer-run process each andevery time for each page requested from a user.

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate further description of the embodiments, the followingdrawings are provided in which:

FIG. 1 illustrates a front elevational view of a computer system that issuitable for implementing an embodiment of the system disclosed in FIGS.3-6;

FIG. 2 illustrates a representative block diagram of an example of theelements included in the circuit boards inside a chassis of the computersystem of FIG. 1;

FIG. 3 illustrates a block diagram of a system that can be automaticallyrendering a webpage on a user device, according to an embodiment;

FIG. 4 illustrates a flow chart for a method, according to anotherembodiment;

FIG. 5 illustrates a flow chart for a method, according to anotherembodiment; and

FIG. 6 illustrates a representative block diagram for automaticallyrendering of a webpage on a user device, according to the embodiment ofFIG. 3.

For simplicity and clarity of illustration, the drawing figuresillustrate the general manner of construction, and descriptions anddetails of well-known features and techniques may be omitted to avoidunnecessarily obscuring the present disclosure. Additionally, elementsin the drawing figures are not necessarily drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help improve understanding of embodimentsof the present disclosure. The same reference numerals in differentfigures denote the same elements.

The terms “first,” “second,” “third,” “fourth,” and the like in thedescription and in the claims, if any, are used for distinguishingbetween similar elements and not necessarily for describing a particularsequential or chronological order. It is to be understood that the termsso used are interchangeable under appropriate circumstances such thatthe embodiments described herein are, for example, capable of operationin sequences other than those illustrated or otherwise described herein.Furthermore, the terms “include,” and “have,” and any variationsthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, system, article, device, or apparatus that comprises alist of elements is not necessarily limited to those elements, but mayinclude other elements not expressly listed or inherent to such process,method, system, article, device, or apparatus.

The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,”“under,” and the like in the description and in the claims, if any, areused for descriptive purposes and not necessarily for describingpermanent relative positions. It is to be understood that the terms soused are interchangeable under appropriate circumstances such that theembodiments of the apparatus, methods, and/or articles of manufacturedescribed herein are, for example, capable of operation in otherorientations than those illustrated or otherwise described herein.

The terms “couple,” “coupled,” “couples,” “coupling,” and the likeshould be broadly understood and refer to connecting two or moreelements mechanically and/or otherwise. Two or more electrical elementsmay be electrically coupled together, but not be mechanically orotherwise coupled together. Coupling may be for any length of time,e.g., permanent or semi-permanent or only for an instant. “Electricalcoupling” and the like should be broadly understood and includeelectrical coupling of all types. The absence of the word “removably,”“removable,” and the like near the word “coupled,” and the like does notmean that the coupling, etc. in question is or is not removable.

As defined herein, two or more elements are “integral” if they arecomprised of the same piece of material. As defined herein, two or moreelements are “non-integral” if each is comprised of a different piece ofmaterial.

As defined herein, “approximately” can, in some embodiments, mean withinplus or minus ten percent of the stated value. In other embodiments,“approximately” can mean within plus or minus five percent of the statedvalue. In further embodiments, “approximately” can mean within plus orminus three percent of the stated value. In yet other embodiments,“approximately” can mean within plus or minus one percent of the statedvalue.

DESCRIPTION OF EXAMPLES OF EMBODIMENTS

To minimize or prevent a viewer of a webpage to have to wait too longfor the webpage to download and display on a screen of a computingdevice of the view, a core code JavaScript for a webpage can be storedin a long-term cache of a user device and the remaining customapplication code can be stored in a cache memory of a separate,special-purpose computer in accordance with many embodiments describedherein. In the same or different embodiments, minimizing or preventing aviewer of a webpage to have to wait too long for the webpage to downloadand display on a screen of a computing device of the view, JavaScriptfor a webpage can be pre-loaded by a service worker on a user device byretrieving custom application code from a cache memory of a separate,special-purpose computer. In these ways, the webpage can be downloadedin real-time, more quickly, and directly to the user device.

Turning to the drawings, FIG. 1 illustrates an exemplary embodiment of acomputer system 100, all of which or a portion of which can be suitablefor (i) implementing part or all of one or more embodiments of thetechniques, methods, and systems and/or (ii) implementing and/oroperating part or all of one or more embodiments of the non-transitorycomputer readable media described herein. As an example, a different orseparate one of computer system 100 (and its internal components, or oneor more elements of computer system 100) can be suitable forimplementing part or all of the techniques described herein. Computersystem 100 can comprise chassis 102 containing one or more circuitboards (not shown), a Universal Serial Bus (USB) port 112, a CompactDisc Read-Only Memory (CD-ROM) and/or Digital Video Disc (DVD) drive116, and a hard drive 114. A representative block diagram of theelements included on the circuit boards inside chassis 102 is shown inFIG. 2. A central processing unit (CPU) 210 in FIG. 2 is coupled to asystem bus 214 in FIG. 2. In various embodiments, the architecture ofCPU 210 can be compliant with any of a variety of commerciallydistributed architecture families.

Continuing with FIG. 2, system bus 214 also is coupled to memory storageunit 208 that includes both read only memory (ROM) and random accessmemory (RAM). Non-volatile portions of memory storage unit 208 or theROM can be encoded with a boot code sequence suitable for restoringcomputer system 100 (FIG. 1) to a functional state after a system reset.In addition, memory storage unit 208 can include microcode such as aBasic Input-Output System (BIOS). In some examples, the one or morememory storage units of the various embodiments disclosed herein caninclude memory storage unit 208, a USB-equipped electronic device (e.g.,an external memory storage unit (not shown) coupled to universal serialbus (USB) port 112 (FIGS. 1-2)), hard drive 114 (FIGS. 1-2), and/orCD-ROM, DVD, Blu-Ray, or other suitable media, such as media configuredto be used in CD-ROM and/or DVD drive 116 (FIGS. 1-2). Non-volatile ornon-transitory memory storage unit(s) refer to the portions of thememory storage units(s) that are non-volatile memory and not atransitory signal. In the same or different examples, the one or morememory storage units of the various embodiments disclosed herein caninclude an operating system, which can be a software program thatmanages the hardware and software resources of a computer and/or acomputer network. The operating system can perform basic tasks such as,for example, controlling and allocating memory, prioritizing theprocessing of instructions, controlling input and output devices,facilitating networking, and managing files. Exemplary operating systemscan includes one or more of the following: (i) Microsoft® Windows®operating system (OS) by Microsoft Corp. of Redmond, Wash., UnitedStates of America, (ii) Mac® OS X by Apple Inc. of Cupertino, Calif.,United States of America, (iii) UNIX® OS, and (iv) Linux® OS. Furtherexemplary operating systems can comprise one of the following: (i) theiOS® operating system by Apple Inc. of Cupertino, Calif., United Statesof America, (ii) the Blackberry® operating system by Research In Motion(RIM) of Waterloo, Ontario, Canada, (iii) the WebOS operating system byLG Electronics of Seoul, South Korea, (iv) the Android™ operating systemdeveloped by Google, of Mountain View, Calif., United States of America,(v) the Windows Mobile™ operating system by Microsoft Corp. of Redmond,Wash., United States of America, or (vi) the Symbian™ operating systemby Accenture PLC of Dublin, Ireland.

As used herein, “processor” and/or “processing module” means any type ofcomputational circuit, such as but not limited to a microprocessor, amicrocontroller, a controller, a complex instruction set computing(CISC) microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, agraphics processor, a digital signal processor, or any other type ofprocessor or processing circuit capable of performing the desiredfunctions. In some examples, the one or more processors of the variousembodiments disclosed herein can comprise CPU 210.

In the depicted embodiment of FIG. 2, various I/O devices such as a diskcontroller 204, a graphics adapter 224, a video controller 202, akeyboard adapter 226, a mouse adapter 206, a network adapter 220, andother I/O devices 222 can be coupled to system bus 214. Keyboard adapter226 and mouse adapter 206 are coupled to a keyboard 104 (FIGS. 1-2) anda mouse 110 (FIGS. 1-2), respectively, of computer system 100 (FIG. 1).While graphics adapter 224 and video controller 202 are indicated asdistinct units in FIG. 2, video controller 202 can be integrated intographics adapter 224, or vice versa in other embodiments. Videocontroller 202 is suitable for refreshing a monitor 106 (FIGS. 1-2) todisplay images on a screen 108 (FIG. 1) of computer system 100 (FIG. 1).Disk controller 204 can control hard drive 114 (FIGS. 1-2), USB port 112(FIGS. 1-2), and CD-ROM and/or DVD drive 116 (FIGS. 1-2). In otherembodiments, distinct units can be used to control each of these devicesseparately.

In some embodiments, network adapter 220 can comprise and/or beimplemented as a WNIC (wireless network interface controller) card (notshown) plugged or coupled to an expansion port (not shown) in computersystem 100 (FIG. 1). In other embodiments, the WNIC card can be awireless network card built into computer system 100 (FIG. 1). Awireless network adapter can be built into computer system 100 (FIG. 1)by having wireless communication capabilities integrated into themotherboard chipset (not shown), or implemented via one or morededicated wireless communication chips (not shown), connected through aPCI (peripheral component interconnector) or a PCI express bus ofcomputer system 100 (FIG. 1) or USB port 112 (FIG. 1). In otherembodiments, network adapter 220 can comprise and/or be implemented as awired network interface controller card (not shown).

Although many other components of computer system 100 (FIG. 1) are notshown, such components and their interconnection are well known to thoseof ordinary skill in the art. Accordingly, further details concerningthe construction and composition of computer system 100 (FIG. 100) andthe circuit boards inside chassis 102 (FIG. 1) are not discussed herein.

When computer system 100 in FIG. 1 is running, program instructionsstored on a USB drive in USB port 112, on a CD-ROM or DVD in CD-ROMand/or DVD drive 116, on hard drive 114, or in memory storage unit 208(FIG. 2) are executed by CPU 210 (FIG. 2). A portion of the programinstructions, stored on these devices, can be suitable for carrying outall or at least part of the techniques described herein. In variousembodiments, computer system 100 can be reprogrammed with one or moremodules, system, applications, and/or databases, such as those describedherein, to convert a general purpose computer to a special purposecomputer. For purposes of illustration, programs and other executableprogram components are shown herein as discrete systems, although it isunderstood that such programs and components may reside at various timesin different storage components of computing device 100, and can beexecuted by CPU 210. Alternatively, or in addition to, the systems andprocedures described herein can be implemented in hardware, or acombination of hardware, software, and/or firmware. For example, one ormore application specific integrated circuits (ASICs) can be programmedto carry out one or more of the systems and procedures described herein.For example, one or more of the programs and/or executable programcomponents described herein can be implemented in one or more ASICs.

Although computer system 100 is illustrated as a desktop computer inFIG. 1, there can be examples where computer system 100 may take adifferent form factor while still having functional elements similar tothose described for computer system 100. In some embodiments, computersystem 100 may comprise a single computer, a single server, or a clusteror collection of computers or servers, or a cloud of computers orservers. Typically, a cluster or collection of servers can be used whenthe demand on computer system 100 exceeds the reasonable capability of asingle server or computer. In certain embodiments, computer system 100may comprise a portable computer, such as a laptop computer. In certainother embodiments, computer system 100 may comprise a mobile device,such as a smartphone. In certain additional embodiments, computer system100 may comprise an embedded system.

Turning ahead in the drawings, FIG. 3 illustrates a block diagram of asystem 300 that can be employed for caching core JavaScript bundles,and/or pre-loading and caching application code, according to anembodiment. System 300 is merely exemplary and embodiments of the systemare not limited to the embodiments presented herein. The system can beemployed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, certain elements,modules, or systems of system 300 can perform various procedures,processes, and/or activities. In other embodiments, the procedures,processes, and/or activities can be performed by other suitableelements, modules, or systems of system 300. In some embodiments, system300 can include an application server 310, and/or a content deliveryserver system 320.

Generally, therefore, system 300 can be implemented with hardware and/orsoftware, as described herein. In some embodiments, part or all of thehardware and/or software can be conventional, while in these or otherembodiments, part or all of the hardware and/or software can becustomized (e.g., optimized) for implementing part or all of thefunctionality of system 300 described herein.

As shown in FIG. 3, system 300 can include application server 310 and/orcontent delivery server 320. Application server 310 and/or contentdelivery server 320 can each be a computer system, such as computersystem 100 (FIG. 1), as described above, and can each be a singlecomputer, a single server, or a cluster or collection of computers orservers, or a cloud of computers or servers. In another embodiment, asingle computer system can host application server 310 and/or contentdelivery server 320. In a number of embodiments, application server 310and/or content delivery server 320 can each be a computer system, suchas computer system 100 (FIG. 1), as described above, and can each be asingle computer, a single server, or a cluster or collection ofcomputers or servers, or a cloud of computers or servers. In anotherembodiment, a single computer system can host application server 310and/or content delivery server 320. Additional details regardingapplication server 310 and/or content delivery server 320 are describedherein.

In a number of embodiments, each of content delivery server 320, and/orapplication server 310 can be a special-purpose computer programedspecifically to perform specific functions not associated with ageneral-purpose computer. In many embodiments, content delivery server320 can be a network of content delivery computers. Similarly, inseveral embodiments, application server 310 can be a network ofapplication computers.

In some embodiments, content delivery server 320 can be aspecial-purpose computer programmed to perform specific functions and/orapplications, such as, receiving application code including JavaScriptbundles (e.g., code) of one or more webpages that can make up an entirewebsite for a retailer (e.g., virtual retailer, on-line retailer,physical store), and storing the application code in a memory (e.g.,cache memory) of the special-purpose computer system. In manyembodiments, content delivery server 320 can be a special-purposecomputer programmed to receive and/or store application code that can besplit (e.g., divided) into a static JavaScript bundle (e.g., core code)and a dynamic JavaScript bundle (e.g., custom application code) of oneor more webpages of a retailer (e.g., virtual retailer, on-lineretailer, physical store) store. Thus, in many embodiments, the one ormore webpages of a website can be stored in a memory (e.g., cachememory) in a special-purpose computer system, such as, content deliveryserver 320.

In several embodiments, content delivery server 320 can be aspecial-purpose computer programmed to perform specific functions and/orapplications, such as, storing application code (e.g., Hypertext MarkupLanguage code, “HTML code”) including JavaScript bundles for each one ofthe multiple webpages that can make up a website. In many embodiments,content delivery server 320 can be a special-purpose programmed toperform specific functions and/or applications, such as, storingapplication code that can be divided into multiple JavaScript bundlesincluding a static JavaScript bundle and a dynamic JavaScript bundle foreach one of the multiple webpages of a website. In many embodiments,content delivery server 320 can be a content delivery network where oneor more content delivery computers can be in data communication with oneanother and vice-versa.

In some embodiments, application server 310 can be a special-purposecomputer programmed to perform specific functions and/or applications,such as, responding to a request from a user device, such as usercomputer 340, 341, by transmitting application code (e.g., HTML code) tothe user device for a client-side webpage rendering process, wherein theapplication code (e.g., HTML code) comprises information that caninclude a location of the JavaScript bundles stored within the contentdelivery computer. Such JavaScript bundles can include a core codeJavaScript bundle and a dynamic JavaScript bundle associated withrendering the requested webpage (e.g., home page, search page, browserpage). In many embodiments, application server 310 can be aspecial-purpose computer programmed to perform specific functions and/orapplications, such as, responding to a request from a user device, suchas user computer 340, 341, by transmitting application code (e.g., HTMLcode) to the user device for a client-side webpage rendering process,wherein the application code (e.g., HTML code) information including anidentification of JavaScript bundles stored in the content deliverycomputer. Such JavaScript bundles can include a core code JavaScriptbundle and a dynamic JavaScript bundle associated with rendering therequested webpage (e.g., home page, search page, browse page).

In a number of embodiments, application server 310, and/or contentdelivery server 320 can be one or more special-purpose computersprogramed specifically to perform functions not associated with ageneral-purpose computer. In several embodiments, application server 310can be a network of computers wherein one or more application computerscan be in data communication with one another and vice versa. In manyembodiments, content delivery server 320 can be a content deliverynetwork where one or more content delivery computers can be in datacommunication with one another and vice-versa.

In many embodiments, application server 310 and/or content deliveryserver 320 can be in data communication through Internet 330 with one ormore user computers, such as user computers 340 and/or 341. In someembodiments, user computers 340, 341 can be used by users, such as users350 and 351, which also can be referred to as customers (e.g., users),in which case, user computers 340 and 341 can be referred to as customercomputers. In many embodiments, am application server 310 can host oneor more websites. For example, application server 310 can host a websitethat allows users to browse and/or search for items (e.g., products), toadd items to an electronic cart, and/or to purchase items, in additionto other suitable activities.

In many embodiments, an internal network that is not open to the publiccan be used for communications between application server 310 and usercomputer 340-341. In several embodiments, an internal network that isnot open to the public can be used for communications between contentserver 320 and user computer 340-341. In some embodiments, anotherinternal network can be used for communications between user computers340-341. In some embodiments, the same or another internal network canbe used for communications between service worker 365, 375 and long-termcache 361, 371, respectively. In some embodiments, the same or anotherinternal network can be used for communications between service worker365, 375 and short-term cache 362, 372, respectively. In someembodiments, the same or another internal network can be used forcommunications between service worker 365, 375 and/or content deliveryserver 320. In some embodiments, the same or another internal networkcan be used for communications between a service worker 365, 375 andcontent delivery server 320 where the communications can be exclusivelyassociated with core code JavaScript. In some embodiments, the same oranother internal network can be used for communications between aservice worker 365, 375 and content delivery server 320 where thecommunications can be exclusively associated with application codeJavaScript. In some embodiments, the same or another internal networkcan be used for communications between a service worker 365, 375,content delivery server 320, and another computer.

Accordingly, in some embodiments, application system 310 (and/or thesoftware used by such systems), and/or content delivery server 320(and/or the software used by such systems) can refer to a back end ofsystem 300 operated by an operator and/or administrator of system 300,and application system 310 (and/or the software used by such systems)can refer to a front end of system 300, as it can be accessed and/orused by one or more users, such as users 350-351, using user computers340-341, respectively. In these or other embodiments, the operatorand/or administrator of system 300 can manage system 300, theprocessor(s) of system 300, and/or the memory storage unit(s) of system300 using the input device(s) and/or display device(s) of system 300.

Additional details regarding application server 310, content deliveryserver 320, and/or service worker 365, 375 are described herein. Inthese or other embodiments, application server 310, content deliveryserver 320, and/or service worker 365, 375 can be located spatiallyapart from each other. Similarly, service worker 365, 375 cancommunicate with content delivery server 320, and/or application server310 can communicate with user computer 340-341, and/or vice versa.

In certain embodiments, user computers 340-341 can be desktop computers,laptop computers, a mobile device, and/or other endpoint devices used byone or more users 350 and 351, respectively. A mobile device can referto a portable electronic device (e.g., an electronic device easilyconveyable by hand by a person of average size) with the capability topresent audio and/or visual data (e.g., text, images, videos, music,etc.). For example, a mobile device can include at least one of adigital media player, a cellular telephone (e.g., a smartphone), apersonal digital assistant, a handheld digital computer device (e.g., atablet personal computer device), a laptop computer device (e.g., anotebook computer device, a netbook computer device), a wearable usercomputer device, or another portable computer device with the capabilityto present audio and/or visual data (e.g., images, videos, music, etc.).Thus, in many examples, a mobile device can include a volume and/orweight sufficiently small as to permit the mobile device to be easilyconveyable by hand. For examples, in some embodiments, a mobile devicecan occupy a volume of less than or equal to approximately 1790 cubiccentimeters, 2434 cubic centimeters, 2876 cubic centimeters, 4056 cubiccentimeters, and/or 5752 cubic centimeters. Further, in theseembodiments, a mobile device can weigh less than or equal to 15.6Newtons, 17.8 Newtons, 22.3 Newtons, 31.2 Newtons, and/or 44.5 Newtons.

Exemplary mobile devices can include (i) an iPod®, iPhone®, iTouch®,iPad®, MacBook® or similar product by Apple Inc. of Cupertino, Calif.,United States of America, (ii) a Blackberry® or similar product byResearch in Motion (RIM) of Waterloo, Ontario, Canada, (iii) a Lumia® orsimilar product by the Nokia Corporation of Keilaniemi, Espoo, Finland,and/or (iv) a Galaxy™ or similar product by the Samsung Group of SamsungTown, Seoul, South Korea. Further, in the same or different embodiments,a mobile device can include an electronic device configured to implementone or more of (i) the iPhone® operating system by Apple Inc. ofCupertino, Calif., United States of America, (ii) the Blackberry®operating system by Research In Motion (RIM) of Waterloo, Ontario,Canada, (iii) the Palm® operating system by Palm, Inc. of Sunnyvale,Calif., United States, (iv) the Android™ operating system developed bythe Open Handset Alliance, (v) the Windows Mobile™ operating system byMicrosoft Corp. of Redmond, Wash., United States of America, or (vi) theSymbian™ operating system by Nokia Corp. of Keilaniemi, Espoo, Finland.

Further still, the term “wearable user computer device” as used hereincan refer to an electronic device with the capability to present audioand/or visual data (e.g., text, images, videos, music, etc.) that isconfigured to be worn by a user and/or mountable (e.g., fixed) on theuser of the wearable user computer device (e.g., sometimes under or overclothing; and/or sometimes integrated with and/or as clothing and/oranother accessory, such as, for example, a hat, eyeglasses, a wristwatch, shoes, etc.). In many examples, a wearable user computer devicecan include a mobile device, and vice versa. However, a wearable usercomputer device does not necessarily include a mobile device, and viceversa.

In specific examples, a wearable user computer device can include a headmountable wearable user computer device (e.g., one or more headmountable displays, one or more eyeglasses, one or more contact lenses,one or more retinal displays, etc.) or a limb mountable wearable usercomputer device (e.g., a smart watch). In these examples, a headmountable wearable user computer device can be mountable in closeproximity to one or both eyes of a user of the head mountable wearableuser computer device and/or vectored in alignment with a field of viewof the user.

In more specific examples, a head mountable wearable user computerdevice can include (i) Google Glass™ product or a similar product byGoogle Inc. of Menlo Park, Calif., United States of America; (ii) theEye Tap™ product, the Laser Eye Tap™ product, or a similar product byePI Lab of Toronto, Ontario, Canada, and/or (iii) the Raptyr™ product,the STAR 1200™ product, the Vuzix Smart Glasses M100™ product, or asimilar product by Vuzix Corporation of Rochester, N.Y., United Statesof America. In other specific examples, a head mountable wearable usercomputer device can include the Virtual Retinal Display™ product, orsimilar product by the University of Washington of Seattle, Wash.,United States of America. Meanwhile, in further specific examples, alimb mountable wearable user computer device can include the iWatch™product, or similar product by Apple Inc. of Cupertino, Calif., UnitedStates of America, the Galaxy Gear or similar product of Samsung Groupof Samsung Town, Seoul, South Korea, the Moto 360 product or similarproduct of Motorola of Schaumburg, Ill., United States of America,and/or the Zip™ product, One™ product, Flex™ product, Charge™ product,Surge™ product, or similar product by Fitbit Inc. of San Francisco,Calif., United States of America.

In many embodiments, application server 310, content delivery server320, and/or user computer 340-341, can each include one or more inputdevices (e.g., one or more keyboards, one or more keypads, one or morepointing devices such as a computer mouse or computer mice, one or moretouchscreen displays, a microphone, etc.), and/or can each include oneor more display devices (e.g., one or more monitors, one or more touchscreen displays, projectors, etc.). In these or other embodiments, oneor more of the input device(s) can be similar or identical to keyboard104 (FIG. 1) and/or a mouse 110 (FIG. 1). Further, one or more of thedisplay device(s) can be similar or identical to monitor 106 (FIG. 1)and/or screen 108 (FIG. 1). The input device(s) and the displaydevice(s) can be coupled to application server 310, content deliveryserver 320, and/or user computer 340-341, in a wired manner and/or awireless manner, and the coupling can be direct and/or indirect, as wellas locally and/or remotely. As an example of an indirect manner (whichmay or may not also be a remote manner), a keyboard-video-mouse (KVM)switch can be used to couple the input device(s) and the displaydevice(s) to the processor(s) and/or the memory storage unit(s). In someembodiments, the KVM switch also can be part of application server 310,content delivery server 320, and/or user computer 340-341. In a similarmanner, the processors and/or the non-transitory computer-readable mediacan be local and/or remote to each other.

In certain embodiments, as illustrated in FIG. 3, user computers 340-341can include service worker 365, 375, and/or cache 360, 370. In someembodiments, cache 360, 370 can include a long-term cache 361, 371, anda short-term cache 362, 372. Long term cache is abbreviated as “LTC” andshort-term cache is abbreviated as “STC” in FIG. 3. In some embodiments,service worker 365, 375 is stored within cache 360, 370, respectively,long-term cache 361, 371, respectively, or short-term cache 362, 372,respectively. In several embodiments, service worker 365, 375 can becomputer script that a browser (e.g., web browser, user device browser)can run in the background away from a main thread of the computerfunctions of user computer 340, 341. In many embodiments, service worker365, 375 can be a web worker and/or a JavaScript file that runsseparately from a main browser on user computer 340, 341 that canintercept and/or receive requests (e.g., user, network) to or from usercomputer 340, 341 and can cache resources (e.g., JavaScript bundles). Insome embodiments, service worker 365, 375 can be run separately fromdownloading a webpage, allowing the service worker to perform computerfunctions and/or features without a webpage and/or user interaction.

Meanwhile, in many embodiments, application server 310, content deliveryserver 320, and/or user computer 340-341 also can be configured tocommunicate with one or more databases. The one or more databases caninclude a product database that contains information about products,items, or SKUs (stock keeping units), for example. The one or moredatabases can be stored on one or more memory storage units (e.g.,non-transitory computer readable media), which can be similar oridentical to the one or more memory storage units (e.g., non-transitorycomputer readable media) described above with respect to computer system100 (FIG. 1). Also, in some embodiments, for any particular database ofthe one or more databases, that particular database can be stored on asingle memory storage unit or the contents of that particular databasecan be spread across multiple ones of the memory storage units storingthe one or more databases, depending on the size of the particulardatabase and/or the storage capacity of the memory storage units.

The one or more databases can each include a structured (e.g., indexed)collection of data and can be managed by any suitable databasemanagement systems configured to define, create, query, organize,update, and manage database(s). Exemplary database management systemscan include MySQL (Structured Query Language) Database, PostgreSQLDatabase, Microsoft SQL Server Database, Oracle Database, SAP (Systems,Applications, & Products) Database, and IBM DB2 Database.

Meanwhile, communication between application server 310, contentdelivery server 320, and/or user computer 340-341, and/or the one ormore databases can be implemented using any suitable manner of wiredand/or wireless communication. Accordingly, system 300 can include anysoftware and/or hardware components configured to implement the wiredand/or wireless communication. Further, the wired and/or wirelesscommunication can be implemented using any one or any combination ofwired and/or wireless communication network topologies (e.g., ring,line, tree, bus, mesh, star, daisy chain, hybrid, etc.) and/or protocols(e.g., personal area network (PAN) protocol(s), local area network (LAN)protocol(s), wide area network (WAN) protocol(s), cellular networkprotocol(s), powerline network protocol(s), etc.). Exemplary PANprotocol(s) can include Bluetooth, Zigbee, Wireless Universal Serial Bus(USB), Z-Wave, etc.; exemplary LAN and/or WAN protocol(s) can includeInstitute of Electrical and Electronic Engineers (IEEE) 802.3 (alsoknown as Ethernet), IEEE 802.11 (also known as WiFi), etc.; andexemplary wireless cellular network protocol(s) can include GlobalSystem for Mobile Communications (GSM), General Packet Radio Service(GPRS), Code Division Multiple Access (CDMA), Evolution-Data Optimized(EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), Universal MobileTelecommunications System (UMTS), Digital Enhanced CordlessTelecommunications (DECT), Digital AMPS (IS-136/Time Division MultipleAccess (TDMA)), Integrated Digital Enhanced Network (iDEN), EvolvedHigh-Speed Packet Access (HSPA+), Long-Term Evolution (LTE), WiMAX, etc.The specific communication software and/or hardware implemented candepend on the network topologies and/or protocols implemented, and viceversa. In many embodiments, exemplary communication hardware can includewired communication hardware including, for example, one or more databuses, such as, for example, universal serial bus(es), one or morenetworking cables, such as, for example, coaxial cable(s), optical fibercable(s), and/or twisted pair cable(s), any other suitable data cable,etc. Further exemplary communication hardware can include wirelesscommunication hardware including, for example, one or more radiotransceivers, one or more infrared transceivers, etc. Additionalexemplary communication hardware can include one or more networkingcomponents (e.g., modulator-demodulator components, gateway components,etc.).

In many embodiments, one or more of the webpages displayed by thewebsite hosted by a web server can include one or more JavaScriptbundles that can render webpages, and/or content elements of webpages.In some embodiments, these content elements of webpages can includeinformation about one or more items that are available on the website.For example, a webpage can include a content element that includes linksto item pages for separate items. In many embodiments, these items canbe featured and/or promoted items on the website. Conventionally, thesecontent elements are designed by merchants, and there are many possiblecontent elements from which to select when displaying one or morecontent elements on a webpage of the website.

Users (e.g., 350-351) can send a request for a webpage (e.g.,dynamically-generated webpage) from user computers 340, 341 toapplication server 310 to receive a visible and/or interactive webpagein return. In some embodiments, users can request webpages in a specificorder and/or sequence that can be most commonly visited webpages of aweb site, including a homepage of the web site, a search page of the website, and so on. In several embodiments, after users visit a specificmost commonly visited webpage of a website, users can request second andthird webpages in a most commonly requested order and/or sequence. Thisorder or sequence can be determined or predicted based on past useractivity and/or behavior on the website. Factors influencing this orderor sequence can include easy navigation, browsing, shopping, andpurchasing of items, among other activities on the webpage. For example,when a user visits a home page of a website, it is highly probable thatthe user subsequently visits or requests a search page and a checkoutpage, based on analytics that indicate these pages are the most commonlyrequested webpages after the homepage is selected. In another example,when a user selects a product page, it is highly probable that the usersubsequently visits or requests, a home page, a search page, and acheckout page.

In several embodiments, application server 310 and/or content deliveryserver 320 can operate various computer processes concurrently by usingone or more processes and/or threads (e.g., basic unit based on anoperating system that can allocate processor time). In many embodiments,using a main thread, user device 340, 341 can be in data communicationwith application server 310 that can execute various computer functions.In some embodiments, using a main thread, user device 340, 341 can be indata communication with content delivery sever 320. In severalembodiments, using a second thread (e.g., a service worker thread),service worker 365, 375 can be in data communication with long-termcache 361, 371, respectively. In various embodiments, via a secondthread, service worker 365, 371 can be in data communication with otherportions of user computer 340, 341, respectively. In many embodiments,via a second thread, service worker 365, 375 can be in datacommunication with content delivery server 320. In several embodiments,using a second thread (e.g., a service worker thread), service worker365, 375 can be in data communication with short-term cache 362, 372,respectively.

In many embodiments, system 300 can provide an automated approach todisplaying a webpage by pre-caching a core bundle of code in long-termcache 361, 371, of user computer 340, 341, where, upon receiving arequest to display a webpage on user computer 340, 341, only the customapplication code remains to be downloaded onto user computer 340, 341 torender and/or visibly display the webpage on user computer 340, 341. Inconventional approaches, each time a user device requests a webpage, aweb server and/or an application server, such as application server 310,had to dynamically generate both a core bundle and a custom applicationcode and then download the same to the user device using a main threadin the main process of the user device which leads to sub-optimalprocessing speed and additional computer resources before the webpagecan be visibly displayed on the user device. However, by using twothreads instead of only a single thread, the webpage can be renderedusing more optimal processing speed and, in some instances, lesscomputer resources before the webpage can be visible and interactive onthe user device. Some experimental results have shown that thetechniques described herein can save approximately 4.5 secondsdownloading a webpage (e.g., home page, check-out page) by pre-loadingJavaScript bundles onto the user device from a content delivery server,using two threads to process a request. In several embodiments,experimental results also have shown that the techniques describedherein can save 3.5 seconds downloading a webpage (e.g., home page,check-out page) by caching core JavaScript bundles in a user device(e.g., user computer 340-341). In many embodiments, a core codeJavaScript bundle can be a type of a universal JavaScript code that canbe stored in a user device cache from a content delivery computer cachewhere each webpage of a website uses the core code JavaScript code,along with a custom application code for each webpage, to render awebpage, such as a home page, a search page, a content page, a productpage, and other such webpages. In some embodiments, the core codeJavaScript can make up more than half of the application code for awebpage, leaving less than half of the application code remaining to bedownloaded upon request from the user device.

In many embodiments, system 300 can provide an automated approach todisplaying a webpage by pre-loading (e.g., pre-fetching) webpages fromcontent delivery server 320 onto user computer 340, 341, where a serviceworker pre-loads the JavaScript bundle into the user computer using asecond thread that does not interfere with the main thread to rendersubsequent webpages most commonly visited after a selection of a firstwebpage. From time-to-time, tracked data for application code includinga core bundle of code and a custom application code can be updated incontent delivery server 320 and long-term cache memory in user computer340, 341.

Turning ahead in the drawings, FIG. 4 illustrates a flow chart for amethod 400. In some embodiments, method 400 can be a method ofautomatically rendering of a webpage on a user device displaying avisible and/or interactive webpage by caching or pre-caching a coreJavaScript bundle in a user device. Method 400 is merely exemplary andis not limited to the embodiments presented herein. Method 400 can beemployed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 400 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 400 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 400 can be combined orskipped.

In many embodiments, system 300 (FIG. 3), application server 310 (FIG.3) and/or content delivery server (FIG. 3) can be suitable to performmethod 400 and/or one or more of the activities of method 400. In theseor other embodiments, one or more of the activities of method 400 can beimplemented as one or more computing instructions configured to run atone or more processors and configured to be stored at one or morenon-transitory computer readable media. Such non-transitory computerreadable media can be part of a computer system such as applicationserver 310 (FIG. 3) and/or content delivery server (FIG. 3). Theprocessor(s) can be similar or identical to the processor(s) describedabove with respect to computer system 100 (FIG. 1).

In some embodiments, method 400 and other activities in method 400 caninclude using a distributed network including distributed memoryarchitecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks by using one or more threadsconcurrently and while still allowing data to be accessible from acentral location.

Referring to FIG. 4, method 400 can comprise an activity 410 ofretrieving application code of a webpage from a website. In someembodiments of activity 410, the application code can include a corecode JavaScript bundle and a dynamic JavaScript bundle. The user devicecan be similar or identical to user computer 340-341 (FIG. 3).

Next, in several embodiments, method 400 also can comprise activity 420of storing the core code JavaScript bundle and the dynamic JavaScriptbundle in a cache of a content delivery computer. In many embodiments,activity 420 can include storing the dynamic JavaScript bundle that alsoincludes custom application code that, together with the core codeJavaScript bundle, can render the webpage using at least a client-siderendering process.

In a number of embodiments, after activity 430, method 400 can compriseactivity 430 of, transmitting to a user device of a user (i) a serviceworker and (ii) the core code JavaScript bundle. The core codeJavaScript bundle can be transmitted from the cache of the contentdelivery computer and can be stored in a long-term cache memory of theuser device.

In several embodiments, activity 430 can comprise activity 431 ofrendering multiple webpages of the website based on using the core codeJavaScript bundle stored in the long-term cache memory of the userdevice. In the same or different embodiments, the multiple webpages ofthe website can be rendered based on using the core code JavaScriptbundle stored in the cache of the content delivery computer.

In several embodiments, activity 430 also can comprise activity 432 ofperiodically updating the custom application code JavaScript bundlestored in the cache of the content delivery computer. In manyembodiments, the content delivery computer or another computer can beprogrammed to conduct the periodic update within the content deliverycomputer an “N” number of times within any period of time and/or timeinterval. In the same or different embodiments, activity 442 isperformed periodically after one or more of activities 440, 450, or 460.

In several embodiments, activity 430 additionally can comprise activity433 of transmitting, via the main thread, a service worker to a userdevice of a user. In some embodiments, a web server and/or anapplication server can initialize a service worker to a user devicewhere the service worker remains to perform specific functions on asecond thread, such as checking the long-term cache on the user devicefor core code JavaScript bundle. In several embodiments, the serviceworker can be programmed to perform additional specific functions and/orfeatures such as checking the content delivery server for a core codeJavaScript bundle when the same has been stored in the long-term cacheof the user device. In many embodiments, a service worker can retrieveapplication code JavaScript bundles from the content delivery computerto download to a user device. In some embodiments, a service worker canretrieve application code JavaScript bundles from the content deliverycomputer to download to short-term cache 362, 372 (FIG. 3) on usercomputer 340-341 (FIG. 3).

In several embodiments, after activity 430, method 400 further cancomprise activity 440 of receiving, via a main thread of the user deviceto an application server, a request from the user device to view thewebpage on the user device. In many embodiments, the webpage can be oneof the webpages on the website that includes one or more differentwebpages. For example, the webpage can be a homepage, a search page, acheck-out page, or another webpage of the web site.

In some embodiments, activity 440 can comprise activity 441 of, inresponse to receiving the request from the user device, applicationserver 310 (FIG. 3) can transmit application code to the user device ifthe same is not already stored on the user device. In some embodiments,application server can relay application code information comprising alocation of core code Java Script and/or custom application codeJavaScript stored in the content delivery computer. In severalembodiments, the core code JavaScript bundle and the dynamic JavaScriptbundle can be associated with rendering the webpage, as requested.

In several embodiments, activity 440 also can comprise activity 442 of,in response to receiving the request from the user device, applicationserver 310 (FIG. 3) can transmit application code to the user device ifthe same is not already stored on the user device, where the applicationserver can relay information that can comprise information comprising anidentity of the core code JavaScript bundle and/or the dynamicJavaScript bundle stored in the content delivery computer. In someembodiments, the core code JavaScript bundle and the dynamic JavaScriptbundle can be associated with rendering the webpage, as requested. Inmany embodiments, the application server can receive requests and relayinformation related to the application code for the requested webpage.In some embodiments, the application server does not store and/ordownload any JavaScript code to content delivery server 320 and/or usercomputer 340-341.

In some embodiments, activity 440 also can comprise activity 443 ofperiodically updating, using the service worker via a second thread ofthe user device to the content delivery computer, each of one or morecore code libraries in the core code JavaScript bundle stored in thelong-term cache memory of the user device. In the same or differentembodiments, activity 443 is performed periodically after one or more ofactivities 450 or 460. The service worker can be similar or identical toservice worker “SW” 365, 375 (FIG. 3). In various embodiments, theapplication code can be divided into a core code JavaScript bundle and acustomer application code bundle, which can be performed in someembodiments by using another computer. In many embodiments, theapplication code, as divided into a core code JavaScript bundle and acustomer application code bundle, can be temporarily cached by anothercomputer prior to caching the separated JavaScript code bundles into thecontent delivery server, such as content delivery server 320 (FIG. 3).In some embodiments, application code for each webpage of a web siteresides in the content delivery server, such as content delivery server320, either in as separated JavaScript code or as a complete JavaScriptcode for the entire webpage. In several embodiments, core codeJavaScript can include core libraries of code used by all other webpageson the website to be rendered into a visible and/or interactive webpage.In many embodiments, custom application code can include code that iscustomized for or used for only one of a homepage, a search page, acontent page, a product page, or other webpages of a website.

In a number of embodiments, after activity 440, method 400 additionallycan comprise activity 450 of, in response to receiving the request,concurrently with the main thread from the user device to theapplication server, determining, using the service worker via the secondthread from the service worker to the long-term cache memory of the userdevice, whether the core code JavaScript bundle for the webpage isstored in the long-term cache memory of the user device. In manyembodiments, activity 450 can be implemented as shown in FIG. 6 anddescribed below.

Next, in a number of embodiments, after activity 450, method 400additionally can comprise activity 460 of, in response to receiving therequest and when the service worker determines that the core codeJavaScript bundle for the webpage is stored in the long-term cachememory of the user device, transmitting, via the main thread from theuser device to the content delivery computer, the custom applicationcode JavaScript bundle directly from the content delivery computer tothe user device. This custom application code JavaScript bundle can beuniquely for the webpage that is requested to be displayed on the userdevice.

In several embodiments, activity 460 can comprise activity 461, of whenthe service worker determines that the core code JavaScript bundle forthe webpage is not stored in the long-term cache memory of the userdevice or elsewhere in the user device, the activity can includerequesting from the content delivery computer, using the service workervia the second thread of the user device to the content deliverycomputer, a core code JavaScript bundle to be used in client-siderendering of the webpage. In many embodiments, activity 461 will not beperformed when activity 460 is performed, and vice versa.

In a number of embodiments, method 400 additionally can compriseactivity 470 of, in response to receiving the request and when theservice worker determines that the core code JavaScript bundle for thewebpage is stored in the long-term cache memory of the user device,facilitating a display of the webpage in a browser of the user deviceusing (i) the dynamic JavaScript bundle, as transmitted from the contentdelivery computer to the user device, and (ii) the core code JavaScriptbundle, as stored in the long-term cache memory of the user device.

Turning ahead in the drawings, FIG. 5 illustrates a flow chart for amethod 500. In some embodiments, method 500 can be a method ofautomatically rendering of a webpage on a user device displaying avisible and/or interactive webpage by pre-loading one or more JavaScriptbundles onto a user device. Method 500 is merely exemplary and is notlimited to the embodiments presented herein. Method 500 can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, the procedures, the processes,and/or the activities of method 500 can be performed in the orderpresented. In other embodiments, the procedures, the processes, and/orthe activities of method 500 can be performed in any suitable order. Instill other embodiments, one or more of the procedures, the processes,and/or the activities of method 500 can be combined or skipped.

In many embodiments, system 300 (FIG. 3), application server 310 (FIG.3) and/or content delivery serve 320 (FIG. 3) can be suitable to performmethod 400 and/or one or more of the activities of method 500. In theseor other embodiments, one or more of the activities of method 500 can beimplemented as one or more computing instructions configured to run atone or more processors and configured to be stored at one or morenon-transitory computer readable media. Such non-transitory computerreadable media can be part of a computer system such as applicationserver 310 and/or content delivery server 320. The processor(s) can besimilar or identical to the processor(s) described above with respect tocomputer system 100 (FIG. 1).

In some embodiments, method 500 and other activities in method 500 caninclude using a distributed network including distributed memoryarchitecture to perform the associated activity. This distributedarchitecture can reduce the impact on the network and system resourcesto reduce congestion in bottlenecks by using one or more threadsconcurrently and while still allowing data to be accessible from acentral location.

Referring to FIG. 5, method 500 can include an activity 510 ofretrieving application code of two or more webpages of a web site torender the two or more webpages on a user device. In many embodiments, afirst portion of the application code can be for rendering a firstwebpage of the two or more webpages of the website and comprises a firstJavaScript bundle, and a second portion of the application code can befor rendering a second webpage of the two or more webpages of thewebsite and can include a second JavaScript bundle. In theseembodiments, the first and second webpages can be different from eachother; the first and second portions of the application code can bedifferent from each other; and the first and second JavaScript bundlescan be different from each other. The user device can be similar oridentical to user computer 340, 341 (FIG. 3). The one or more websitescan be similar or identical to the website hosted by web server and/orapplication server 310 (FIG. 3), as described above.

In several embodiments, activity 510 can include an activity 511 ofrendering the two or more webpages of the website stored in the cachememory of the content delivery server.

In a number of embodiments, after activity 520, method 500 can includean activity 520 of storing the first portion and the second portion ofthe application code of the two or more webpages of the web site in acache memory of a content delivery server.

Next, in several embodiments, method 500 can continue with an activity530 of receiving a request from a user device of a user to display awebpage of the one or more websites on the user device. In manyembodiments, the webpage can be one of the webpages on the web site thatincludes one or more content elements and/or interactive elements. Forexample, the webpage can be a homepage of the website, or anotherwebpage of the website that includes one or more content elements.

In several embodiments, after activity 530, method 500 further caninclude an activity 540 of, in response to receiving the first requestand prior to receiving, from the user device of the user, a secondrequest to view the second webpage on the user device, transmitting thefirst and second portions of the application code to the user device. Insome embodiments, activity 540 can include transmitting, via the mainthread from the user device to the content delivery server, the firstportion of the application code to the user device to render the firstwebpage on the user device. In several embodiments, the first portion ofthe application code can be sent from the cache memory of the contentdelivery server to the user device. In the same or differentembodiments, activity 540 also can include transmitting, using theservice worker via a second thread from the user device to the contentdelivery server, the second portion of the application code to the userdevice for storage on the user device. In many embodiments, the secondportion of the application code can be sent from the cache memory of thecontent delivery server to the user device. In many embodiments,transmitting the first and second portions of the application code tothe user device can occur concurrently with each other via the main andsecond threads from the user device to the content delivery server.

As explained above, the simultaneous transmission of the first andsecond portion of the application code (or at least the transmission ofthe second portion of the application code) before receiving a requestto display the second webpage that requires the use of the secondportion of the application code, can provide the advantages describedabove of reducing, minimizing, or eliminating a delay between the userrequesting the webpage and the user viewing the webpage. As alsoexplained above, the particular application code to be downloaded as thesecond portion of the application code can be determined based on pastuser activity as to which webpage(s) are most likely to be requestednext by the user after viewing the first webpage.

Activity 540 also can include facilitating a display of the firstwebpage on the user device using the first portion of the applicationcode stored on the user device. In some embodiments, this additionalaction within activity 540 can occur via the main thread from the userdevice to the content delivery server, and in other embodiments, thisadditional action within activity 540 can occur via the second threadfrom the user device to the content delivery server.

As shown in FIG. 5, in a number of embodiments, activity 540 also caninclude an activity 541, of transmitting the service worker to the userdevice of the user. Activity 541 can occur via the main thread from theuser device to the application server, or via the main thread from theuser device to the content delivery server. Also, activity 541 isoptional and can be skipped if the service worker was previouslytransmitted to the user device and stored on the user device.Accordingly, activity 541 can include an activity of determining whetherthe service worker is already stored on the user device.

In various embodiments, activity 540 can include an activity 542 ofperiodically updating, using the service worker via the second threadfrom the user device to the content delivery server, each of the firstand second portions of the application code for the first and secondwebpages of the two or more webpages on the user device. In some ofthese embodiments, activity 542 periodically updates, using the serviceworker via the second thread from the user device to the contentdelivery server, the second portion of the application code for thesecond webpage of the two or more webpages on the user device before thesystem receives a request to display the second webpage that requiresthe use of the second portion of the application code.

In several embodiments, after activity 540, method 500 further caninclude an activity 550 of, after transmitting the first and secondportions of the application code to the user device, receiving, via themain thread from the user device to the application server, the secondrequest to view the second webpage on the user device.

Next, in some embodiments, method 500 further can include an activity560 of, in response to receiving the second request, facilitating, usingthe service worker and via the second thread from the user device to thecontent delivery server, a display of the second webpage on the userdevice using the second portion of the application code stored on theuser device. In other embodiments, activity 560 can occur via the mainthread from the user device to the content delivery server.

In many embodiments, activity 560 also can include activity 561 offacilitating a display of the second webpage on the user device based ona client-side rendering process. In many embodiments, activity 561 ispart of or replaces activity 560, and is not a separate or additionalprocess from activity 560.

In various embodiments, activity 560 also can include an activity 562can transmitting a third portion of the application code to the userdevice for storage on the user device. The third portion of theapplication code can be for rendering a third webpage of the two or morewebpages of the web site and can comprise a third JavaScript bundle. Thefirst, second, and third webpages can different from each other; thefirst, second, and third portions of the application code are differentfrom each other; and the first, second, and third JavaScript bundles aredifferent from each other. Activity 562 can occur in response toreceiving the second request and prior to receiving, from the userdevice of the user, the third request to view the third webpage of thetwo or more webpages of the web site on the user device. As explainedabove, the particular application code to be downloaded as the thirdportion of the application code can be determined based on past useractivity as to which webpage(s) are most likely to be requested next bythe user after viewing the second webpage.

In some embodiments, the transmission of the third portion of theapplication code to the user device in activity 562 can occur using theservice worker via the second thread from the user device to the contentdelivery server. In other embodiments, the transmission of the thirdportion of the application code to the user device in activity 562 canoccur via the main thread from the user device to the content deliveryserver. In either of these embodiments, transmitting the third portionof the application to the user device can occur concurrently withactivity 560 of facilitating the display of the second webpage on theuser device. In one example, activities 560 and 562 can occurconcurrently with each other via the main thread from the user device tothe content delivery server for activity 560 and via the second threadfrom the user device to the content delivery server for activity 562.

Also, in these embodiments, after transmitting the third portion of theapplication code to the user device in activity 562, method 500 caninclude receiving, via the main thread from the user device to theapplication server, the third request to view the third webpage on theuser device. Then, in response to receiving the third request, method500 can include facilitating, using the service worker and via thesecond thread from the user device to the content delivery server, adisplay of the third webpage on the user device using the third portionof the application code stored on the user device. In other embodiments,facilitating the display of the third webpage on the user device usingthe third portion of the application code stored on the user device canoccur via the main thread from the user device to the content deliveryserver.

Turning back in the drawings, FIG. 6 illustrates a block diagram ofsystem 300, according to the embodiment shown in FIG. 3. Applicationserver 310, content delivery server 320, and/or service worker 365 aremerely exemplary and are not limited to the embodiments presentedherein. Application server 310, content delivery server 320, and/orservice worker 365 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, certain elements or systems of Application server 310,content delivery server 320, and/or service worker 365 can performvarious procedures, processes, and/or acts. In other embodiments, theprocedures, processes, and/or acts can be performed by other suitableelements or systems. In many embodiments, the systems of applicationserver 310, content delivery server 320, and/or service worker 365 canbe modules of computing instructions (e.g., software modules) stored atnon-transitory computer readable media. In other embodiments, thesystems of application server 310, content delivery server 320, and/orservice worker 365 can be implemented in hardware.

In many embodiments, application server 310 can include a communicationsystem 611. In certain embodiments, communication system 611 can atleast partially perform activity 430 (FIG. 4) of transmitting to a userdevice of a user (i) a service worker and (ii) the core code JavaScriptbundle, wherein the core code JavaScript bundle can be transmitted fromthe cache of the content delivery computer and can be stored in along-term cache memory of the user device, activity 431 of renderingmultiple webpages of the website based on using the core code JavaScriptbundle that can be stored in the long-term cache memory of the userdevice, activity 432 (FIG. 4) of periodically updating the customapplication code in the dynamic JavaScript bundle stored in the cache ofthe content delivery computer, activity 433 (FIG. 4) of transmitting,via the main thread, a service worker to a user device of a user,activity 440 (FIG. 4) of receiving, via a main thread of the user deviceto an application server, a request from the user device to view thewebpage on the user device, activity 441 (FIG. 4) of in response toreceiving the request from the user device, transmitting applicationcode to the user device, wherein the application code comprisesinformation comprising a location, activity 442 (FIG. 4) of, in responseto receiving the request from the user device, transmitting applicationcode to the user device, wherein the application code comprisesinformation comprising an identity, activity 530 (FIG. 5) of receiving,via a main thread from a user device to an application server, a firstrequest from the user device to view the first webpage on the userdevice, activity 540 (FIG. 5) of prior to receiving, from the userdevice of the user, a second request to view the second webpage on theuser device, transmitting the first portion of the application code tothe user device and transmitting the second portion of the applicationcode to the user device and/or activity 550 (FIG. 5) of receiving, viathe main thread from the user device to the application server, thesecond request to view the second webpage on the user device. In someembodiments, transmitting the first and second portions of theapplication code can result in the first and second portions of theapplication code being stored in the short-term cache memory of the userdevice. In other embodiments, transmitting the first and second portionsof the application code can result in the first and second portions ofthe application code being stored in the long-term cache memory of theuser device.

In a number of embodiments, content delivery server 320 can include acommunication system 621. In certain embodiments, user classificationsystem 612 can at least partially perform activity 410 (FIG. 4) ofretrieving application code of a webpage from a website where theapplication code comprises a core code JavaScript bundle and a dynamicJavaScript bundle, activity 411 (FIG. 4) of periodically updating, usingthe service worker via the second thread of the user device to thecontent delivery computer, each of one or more core code libraries inthe core code JavaScript bundle stored in the long-term cache memory ofthe user device, activity 470 (FIG. 4) of facilitating a display of thewebpage in a browser of the user device using (i) the dynamic JavaScriptbundle, as transmitted from the content delivery computer to the userdevice, and (ii) the core code JavaScript bundle, as stored in thelong-term cache memory of the user device, activity 510 (FIG. 5) ofretrieving application code of two or more webpages of a web site torender the two or more webpages on a user device, and/or activity 511(FIG. 5) of rendering the two or more webpages of the web site stored inthe cache memory of the content delivery server.

In many of embodiments, content delivery server 320 can include a memorysystem 632. In certain embodiments, memory system 632 can at leastpartially perform activity 420 (FIG. 4) determining, using the serviceworker via a second thread of the service worker to the long-term cachememory of the user device, whether the core code JavaScript bundle forthe webpage is stored in the long-term cache memory of the user deviceand/or activity 520 (FIG. 5) of storing the first portion and the secondportion of the application code of the two or more webpages of thewebsite in a cache memory of a content delivery server.

In a number of embodiments, service worker system 365 can include acommunication system 631. In certain embodiments, communication system631 can at least partially perform activity 460 (FIG. 4) oftransmitting, via the main thread from the user device to the contentdelivery computer, the dynamic JavaScript bundle for the webpage fromthe content delivery computer to the user device, activity 542 (FIG. 5)of transmitting, via the main thread, a service worker to a user deviceof a user, activity 560 (FIG. 5) of facilitating, using the serviceworker and via the second thread from the user device to the contentdelivery server, a display of the second webpage on the user deviceusing the second portion of the application code stored on the userdevice, activity 561 (FIG. 5) of facilitating a display of the firstwebpage on the user device based on a client-side rendering process,and/or activity 562 (FIG. 5) of facilitating the display of the firstwebpage further comprises the transmitting the first portion of theapplication code to the user device.

In many embodiments, service worker system 365 can include adetermination system 632. In certain embodiments, determination system632 can at least partially perform activity 450 (FIG. 4) transmitting,via the main thread from the user device to the content deliverycomputer, the dynamic JavaScript bundle for the webpage from the contentdelivery computer to the user device, activity 461 (FIG. 4) of when theservice worker determines that the core code JavaScript bundle for thewebpage is not stored in the long-term cache memory of the user device,requesting from the content delivery computer, using the service workervia the second thread of the user device to the content deliverycomputer, the core code JavaScript bundle to be used in client-siderendering of the webpage, and/or activity 541 (FIG. 5) of periodicallyupdating, using the service worker via the second thread from the userdevice to the content delivery server, each of the first and secondportions of the application code for the first and second webpages ofthe two or more webpages.

Various embodiments can include a system including one or moreprocessors and one or more non-transitory computer-readable mediastoring computing instructions configured to run on the one moreprocessors and perform certain acts. The acts can include retrievingapplication code of a webpage from a website. The acts also can includethe application code comprising a core code JavaScript bundle and adynamic JavaScript bundle. The acts can include storing the core codeJavaScript bundle and the dynamic JavaScript bundle in a cache of acontent delivery computer. The cache of a content delivery computer caninclude the dynamic JavaScript bundle that can include customapplication code to render the webpage. The acts further can includetransmitting to a user device of a user a service worker and the corecode JavaScript bundle. The core code JavaScript bundle can betransmitted from the cache of the content delivery computer and can bestored in a long-term cache memory of the user device. The acts caninclude receiving, via a main thread from the user device to anapplication server, a request from the user device to view the webpageon the user device. In response to receiving the request, the acts canconcurrently with the main thread from the user device to theapplication server, can be determining, using the service worker via asecond thread from the service worker to the long-term cache memory ofthe user device, whether the core code JavaScript bundle for the webpageis stored in the long-term cache memory of the user device. When theservice worker determines that the core code JavaScript bundle for thewebpage is stored in the long-term cache memory of the user device, theacts can include transmitting, via the main thread from the user deviceto the content delivery computer, the dynamic JavaScript bundle for thewebpage from the content delivery computer to the user device. The actscan include facilitating a display of the webpage in a browser of theuser device using the dynamic JavaScript bundle, as transmitted from thecontent delivery computer to the user device. The acts further includefacilitating a display of the webpage in a browser of the user deviceusing the core code JavaScript bundle, as stored.

A number of embodiments can include a method being implemented viaexecution of computing instructions configured to run at one or moreprocessors and stored at one or more non-transitory computer-readablemedia. The method can include retrieving application code of a webpagefrom a website. The method also can include retrieving the applicationcode including a core code JavaScript bundle and a dynamic JavaScriptbundle. The method can include storing the core code JavaScript bundleand the dynamic JavaScript bundle in a cache of a content deliverycomputer. The method additionally can include storing the dynamicJavaScript bundle that can include custom application code to render thewebpage. The method can include transmitting to a user device of a user(i) a service worker and (ii) the core code JavaScript bundle. Themethod can include the core code JavaScript bundle that can betransmitted from the cache of the content delivery computer and can bestored in a long-term cache memory of the user device. The method alsocan include receiving, via a main thread from the user device to anapplication server, a request from the user device to view the webpageon the user device. In response to receiving the request, concurrentlywith the main thread from the user device to the application server, themethod can include determining, using the service worker via a secondthread from the service worker to the long-term cache memory of the userdevice, whether the core code JavaScript bundle for the webpage isstored in the long-term cache memory of the user device. When theservice worker determines that the core code JavaScript bundle for thewebpage is stored in the long-term cache memory of the user device, themethod also can include transmitting, via the main thread from the userdevice to the content delivery computer, the dynamic JavaScript bundlefor the webpage from the content delivery computer to the user device.The method can include facilitating a display of the webpage in abrowser of the user device using the dynamic JavaScript bundle, astransmitted from the content delivery computer to the user device. Themethod can include facilitating a display of the webpage in a browser ofthe user device using the core code JavaScript bundle, as stored in thelong-term cache memory of the user device.

Various embodiments can include a system including one or moreprocessors and one or more non-transitory computer-readable mediastoring computing instructions configured to run on the one moreprocessors and perform certain acts. The acts can include retrievingapplication code of two or more webpages of a website to render the twoor more webpages on a user device. A first portion of the applicationcode is for rendering a first webpage of the two or more webpages of thewebsite can include a first JavaScript bundle. A second portion of theapplication code can be used for rendering a second webpage of the twoor more webpages of the website and can include a second JavaScriptbundle. The first and second webpages can be different from each other.The first and second portions of the application code also can bedifferent from each other, and the first and second JavaScript bundlescan be different from each other. The acts can include storing the firstportion and the second portion of the application code of the two ormore webpages of the website in a cache memory of a content deliveryserver. The acts can include receiving, via a main thread from a userdevice to an application server, a first request from the user device toview the first webpage on the user device. In response to receiving thefirst request and prior to receiving, from the user device of the user,a second request to view the second webpage on the user device the actscan include transmitting, via the main thread from the user device tothe content delivery server, the first portion of the application codeto the user device to render the first webpage on the user device. Thefirst portion of the application code can be sent from the cache memoryof the content delivery server to the user device. In response toreceiving the first request and prior to receiving, from the user deviceof the user, a second request to view the second webpage on the userdevice the acts also can include transmitting, using a service workervia a second thread from the user device to the content delivery server,the second portion of the application code to the user device forstorage on the user device. The second portion of the application codecan be sent from the cache memory of the content delivery server to theuser device. Transmitting the first and second portions of theapplication code to the user device can occur concurrently with eachother via the main and second threads from the user device to thecontent delivery server. After transmitting the first and secondportions of the application code to the user device, the acts can bereceiving, via the main thread from the user device to the applicationserver, the second request to view the second webpage on the userdevice. The acts can also include, in response to receiving the secondrequest, facilitating, using the service worker and via the secondthread from the user device to the content delivery server, a display ofthe second webpage on the user device using the second portion of theapplication code stored on the user device.

Many embodiments can include a method being implemented via execution ofcomputing instructions configured to run at one or more processors andstored at one or more non-transitory computer-readable media. The methodcan include retrieving application code of two or more webpages of awebsite to render the two or more webpages on a user device. A firstportion of the application code can be for rendering a first webpage ofthe two or more webpages of the website and can include a firstJavaScript bundle. A second portion of the application code can be forrendering a second webpage of the two or more webpages of the websiteand can include a second JavaScript bundle. The first and secondwebpages can be different from each other. The first and second portionsof the application code can be different from each other. The first andsecond JavaScript bundles also can be different from each other. Themethod can include storing the first portion and the second portion ofthe application code of the two or more webpages of the web site in acache memory of a content delivery server. The method can also includereceiving, via a main thread from a user device to an applicationserver, a first request from the user device to view the first webpageon the user device. In response to receiving the first request and priorto receiving, from the user device of the user, a second request to viewthe second webpage on the user device, the method can be transmitting,via the main thread from the user device to the content delivery server,the first portion of the application code to the user device to renderthe first webpage on the user device. The first portion of theapplication code can be sent from the cache memory of the contentdelivery server to the user device. Prior to receiving, from the userdevice of the user, a second request to view the second webpage on theuser device, the method also can be transmitting, using a service workervia a second thread from the user device to the content delivery server,the second portion of the application code to the user device forstorage on the user device. The second portion of the application codecan be sent from the cache memory of the content delivery server to theuser device. Transmitting the first and second portions of theapplication code to the user device can be occurring concurrently witheach other via the main and second threads from the user device to thecontent delivery server. After transmitting the first and secondportions of the application code to the user, the method can bereceiving, via the main thread from the user device to the applicationserver, the second request to view the second webpage on the userdevice. The method can include, in response to receiving the secondrequest, facilitating, using the service worker and via the secondthread from the user device to the content delivery server, a display ofthe second webpage on the user device using the second portion of theapplication code stored on the user device.

Although automatically rendering of a webpage on a user devicedisplaying a visible and/or interactive webpage by caching a coreJavaScript bundle in a user device has been described with reference tospecific embodiments, it will be understood by those skilled in the artthat various changes may be made without departing from the spirit orscope of the disclosure. Additionally, although automatically renderingof a webpage on a user device displaying a visible and/or interactivewebpage by pre-loading one or more JavaScript bundles in a user devicehas been described with reference to specific embodiments, it will beunderstood by those skilled in the art that various changes may be madewithout departing from the spirit or scope of the disclosure.Accordingly, the disclosure of embodiments is intended to beillustrative of the scope of the disclosure and is not intended to belimiting. It is intended that the scope of the disclosure shall belimited only to the extent required by the appended claims. For example,to one of ordinary skill in the art, it will be readily apparent thatany element of FIGS. 1-6 may be modified, and that the foregoingdiscussion of certain of these embodiments does not necessarilyrepresent a complete description of all possible embodiments. Forexample, one or more of the procedures, processes, or activities ofFIGS. 4-6 may include different procedures, processes, and/or activitiesand be performed by many different modules, in many different orders,and/or one or more of the procedures, processes, or activities of FIGS.4-6 may include one or more of the procedures, processes, or activitiesof another different one of FIGS. 4-6. As another example, the systemswithin application system 310, content delivery system 320 and/orservice worker 365 in FIG. 6 can be interchanged or otherwise modified.Furthermore, code described to be stored in cache can be stored inlong-term cache or short-term cache. For example, code described to bestored in long-term cache can be stored in short-term cache, and viceversa.

Replacement of one or more claimed elements constitutes reconstructionand not repair. Additionally, benefits, other advantages, and solutionsto problems have been described with regard to specific embodiments. Thebenefits, advantages, solutions to problems, and any element or elementsthat may cause any benefit, advantage, or solution to occur or becomemore pronounced, however, are not to be construed as critical, required,or essential features or elements of any or all of the claims, unlesssuch benefits, advantages, solutions, or elements are stated in suchclaim.

Moreover, embodiments and limitations disclosed herein are not dedicatedto the public under the doctrine of dedication if the embodiments and/orlimitations: (1) are not expressly claimed in the claims; and (2) are orare potentially equivalents of express elements and/or limitations inthe claims under the doctrine of equivalents.

What is claimed is:
 1. A system comprising: one or more processors; andone or more non-transitory computer-readable media storing computinginstructions configured, when executed by the one or more processors, toperform: retrieving application code of a webpage from a website, theapplication code comprising a core code JavaScript bundle and a dynamicJavaScript bundle; storing the core code JavaScript bundle and thedynamic JavaScript bundle in a cache of a content delivery computer,wherein the dynamic JavaScript bundle comprises custom application codeto render the webpage; transmitting to a user device of a user (i) aservice worker and (ii) the core code JavaScript bundle, wherein thecore code JavaScript bundle is transmitted from the cache of the contentdelivery computer and is stored in a long-term cache memory of the userdevice; receiving, via a main thread from the user device to anapplication server, a request from the user device to view the webpageon the user device; and in response to receiving the request:concurrently with the main thread from the user device to theapplication server, determining, using the service worker via a secondthread from the service worker to the long-term cache memory of the userdevice, whether the core code JavaScript bundle for the webpage isstored in the long-term cache memory of the user device; when theservice worker determines that the core code JavaScript bundle for thewebpage is stored in the long-term cache memory of the user device,transmitting, via the main thread from the user device to the contentdelivery computer, the dynamic JavaScript bundle for the webpage fromthe content delivery computer to the user device; and facilitating adisplay of the webpage in a browser of the user device using (i) thedynamic JavaScript bundle, as transmitted from the content deliverycomputer to the user device, and (ii) the core code JavaScript bundle,as stored in the long-term cache memory of the user device, wherein thecore code JavaScript bundle and the dynamic JavaScript bundle arecombined to be used for client-side rendering of the webpage.
 2. Thesystem of claim 1, wherein the computing instructions are furtherconfigured, when executed by the one or more processors, to perform:facilitating client-side rendering of multiple webpages of the websitebased on using the core code JavaScript bundle stored in the long-termcache memory of the user device.
 3. The system of claim 1, wherein thecomputing instructions are further configured, when executed by the oneor more processors, to perform: periodically updating, using the serviceworker via the second thread from the user device to the contentdelivery computer, each of one or more core code libraries in the corecode JavaScript bundle stored in the long-term cache memory of the userdevice.
 4. The system of claim 1, wherein the computing instructions arefurther configured, when executed by the one or more processors, toperform: periodically updating the custom application code in thedynamic JavaScript bundle stored in the cache of the content deliverycomputer.
 5. The system of claim 1, wherein the computing instructionsare further configured, when executed by the one or more processors, toperform: when the service worker determines that the core codeJavaScript bundle for the webpage is not stored in the long-term cachememory of the user device: requesting from the content deliverycomputer, using the service worker via the second thread from the userdevice to the content delivery computer, the core code JavaScript bundleto be used in the client-side rendering of the webpage.
 6. The system ofclaim 5, wherein: requesting from the content delivery computer, usingthe service worker via the second thread from the user device to thecontent delivery computer, the core code JavaScript bundle furthercomprises: retrieving a first core code JavaScript bundle.
 7. The systemof claim 1, wherein the computing instructions, when executed by the oneor more processors, are further configured to perform: in response toreceiving the request from the user device, transmitting applicationcode to the user device, wherein the application code comprisesinformation comprising a location in the content delivery computer ofthe core code JavaScript bundle and the dynamic JavaScript bundleassociated with rendering the webpage, as requested.
 8. The system ofclaim 1, the computing instructions, when executed by the one or moreprocessors, are further configured to perform: in response to receivingthe request from the user device, transmitting application code to theuser device, wherein the application code comprises informationcomprising an identity of the core code JavaScript bundle and thedynamic JavaScript bundle in the content delivery computer, wherein thecore code JavaScript bundle and the dynamic JavaScript bundle areassociated with rendering the webpage, as requested.
 9. The system ofclaim 1, wherein transmitting to the user device of the user (i) theservice worker and (ii) the core code JavaScript bundle comprises:transmitting, via the main thread from the user device, the serviceworker to the user device of the user.
 10. A method being implementedvia execution of computing instructions configured to run at one or moreprocessors and stored at one or more non-transitory computer-readablemedia, the method comprising: retrieving application code of a webpagefrom a website, the application code comprising a core code JavaScriptbundle and a dynamic JavaScript bundle; storing the core code JavaScriptbundle and the dynamic JavaScript bundle in a cache of a contentdelivery computer, wherein the dynamic JavaScript bundle comprisescustom application code to render the webpage; transmitting to a userdevice of a user (i) a service worker and (ii) the core code JavaScriptbundle, wherein the core code JavaScript bundle is transmitted from thecache of the content delivery computer and is stored in a long-termcache memory of the user device; receiving, via a main thread from theuser device to an application server, a request from the user device toview the webpage on the user device; and in response to receiving therequest: concurrently with the main thread from the user device to theapplication server, determining, using the service worker via a secondthread from the service worker to the long-term cache memory of the userdevice, whether the core code JavaScript bundle for the webpage isstored in the long-term cache memory of the user device; when theservice worker determines that the core code JavaScript bundle for thewebpage is stored in the long-term cache memory of the user device,transmitting, via the main thread from the user device to the contentdelivery computer, the dynamic JavaScript bundle for the webpage fromthe content delivery computer to the user device; and facilitating adisplay of the webpage in a browser of the user device using (i) thedynamic JavaScript bundle, as transmitted from the content deliverycomputer to the user device, and (ii) the core code JavaScript bundle,as stored in the long-term cache memory of the user device, wherein thecore code JavaScript bundle and the dynamic JavaScript bundle arecombined to be used for client-side rendering of the webpage.
 11. Themethod of claim 10, further comprising: facilitating client-siderendering of multiple webpages of the website based on using the corecode JavaScript bundle stored in the long-term cache memory of the userdevice.
 12. The method of claim 10, further comprising: periodicallyupdating, using the service worker via the second thread from the userdevice to the content delivery computer, each of one or more core codelibraries in the core code JavaScript bundle stored in the long-termcache memory of the user device.
 13. The method of claim 10, furthercomprising: periodically updating the custom application code in thedynamic JavaScript bundle stored in the cache of the content deliverycomputer.
 14. The method of claim 10, further comprising: when theservice worker determines that the core code JavaScript bundle for thewebpage is not stored in the long-term cache memory of the user device:requesting from the content delivery computer, using the service workervia the second thread from the user device to the content deliverycomputer, the core code JavaScript bundle to be used in the client-siderendering of the webpage.
 15. The method of claim 14, wherein requestingfrom the content delivery computer, using the service worker via thesecond thread from the user device to the content delivery computer, thecore code JavaScript bundle further comprises: retrieving a first corecode JavaScript bundle.
 16. The method of claim 10, further comprising:in response to receiving the request from the user device, transmittingapplication code to the user device, wherein the application codecomprises information comprising a location in the content deliverycomputer of the core code JavaScript bundle and the dynamic JavaScriptbundle associated with rendering the webpage, as requested.
 17. Themethod of claim 10, further comprising: in response to receiving therequest from the user device, transmitting application code to the userdevice, wherein the application code comprises information comprising anidentity of the core code JavaScript bundle and the dynamic JavaScriptbundle in the content delivery computer, wherein the core codeJavaScript bundle and the dynamic JavaScript bundle are associated withrendering the webpage, as requested.
 18. The method of claim 10, whereintransmitting to the user device of the user (i) the service worker and(ii) the core code JavaScript bundle comprises: transmitting, via themain thread of the user device, the service worker to the user device ofthe user.
 19. The system of claim 6, wherein the first core codeJavaScript bundle is cached in the long-term cache memory of the userdevice.
 20. The method of claim 15, wherein the first core codeJavaScript bundle is cached in the long-term cache memory of the userdevice.